Skip to content

Fix occasional "failed to acquire scoreboard" warning #9019

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Conversation

Nilix007
Copy link
Contributor

With request timeouts configured, php-fpm occasionally prints the
following warning:

WARNING: failed to acquire scoreboard

This is happens when php-fpm checks the child scoreboards for timeouts,
but fails to acquire a lock immediately. As this can (and does) occur
during normal operation, this commit simply removes the warning
altogether.

@devnexen
Copy link
Member

Not sure if we should completely remove the info. cc @bukka

@bukka
Copy link
Member

bukka commented Jul 16, 2022

@Nilix007 Do you see a lot of those? I think if this is happening a lot, then it can't degrade the functionality of slowlog - not logging all slow requests. We might need to look into improving the scoreboard locking in such case.

I agree that warning is not the right level if you can't do anything about this. However it might still be quite useful to now if slowlog might potentially miss some items. So I would suggest to just lower the log level and instead use ZLOG_NOTICE.

@Nilix007
Copy link
Contributor Author

Do you see a lot of those?

About twice a day, so not too often.

So I would suggest to just lower the log level and instead use ZLOG_NOTICE.

Sure, I'll update the PR 👍

With request timeouts configured, php-fpm occasionally prints the
following warning:

   WARNING: failed to acquire scoreboard

This is happens when php-fpm checks the child scoreboards for timeouts,
but fails to acquire a lock immediately.  As this can (and does) occur
during normal operation, this commit downgrades this to a notice.
@Nilix007 Nilix007 force-pushed the fix_failed_to_acquire_scoreboard_warning branch from ef75955 to e90a564 Compare July 18, 2022 06:28
Copy link
Member

@devnexen devnexen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@devnexen devnexen closed this in 3040f75 Jul 18, 2022
@devnexen
Copy link
Member

Thank you !

@bukka
Copy link
Member

bukka commented Jul 18, 2022

I'm not sure we should be merging that to 8.0 because this is not really a bug and there is minor chance that some tools are configured to deal with specific messages from logs even though it's a small chance we still shouldn't do that.

@devnexen Please could you revert this from 8.0 and 8.1 and keep it only in master?

@devnexen
Copy link
Member

Sorry my mistake, reverted.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants